Hunt Groups (Networked)

Description

Networked hunt groups provide hunt group functionality across a network or cluster.

Conditions and Feature Interactions

• The controller of a network hunt group must be running Release 7.0 or later software.

• A remote hunt group member is one that is not either a primary or secondary device on the hunt group host. These remote members must be accessed via trunks that use DPNSS signaling (T1/E1 DPNSS, XNET, or IP trunks). Access via QSIG signaling is not supported.

• Only Voice hunt group can be networked.

• Uniform Call Distribution (UCD) hunt groups cannot be networked. RADs should not be programmed against voice hunt groups with remote members, and remote members should not be programmed against voice hunt groups with RADs.

• Valid members of a network hunt group include:

• local stations or Broadcast Group A directory number programmed to appear on multiple devices constitutes a broadcast group. There are two types of broadcast groups: Non-Prime Line and Prime Line. A Non-Prime Line group is a directory number programmed on one or more devices that is not the prime line on any device. A Prime Line group is a directory number programmed on button 0 of a phone. Server-based variants of MiVoice Business that use x86 processors, MiVoice Business for Industry Standard Servers MCD-ISS), Multi-instance MiVoice Business, and Virtual MiVoice Business, up to 250 appearances of the directory number can appear on one or more devices. For all other 3300 ICP/MiVoice Business call control platforms, up to 32 appearances of the directory number may appear on one or more devices.

• remote directory numbers (RDNs)

• system speedcall numbers.

• Remote members are programmed in the hunt group as RDNs or system speed call digits. Voice terminals in another vendor's network are valid network hunt group members (programmed as system speed call digits).

• If another call arrives to a network hunt group that is already being hunted, the new call proceeds through the member list in parallel with the existing call(s) to the group.

• If using terminal hunting for a hunt group, place the local members at the beginning of the member list.

• If using circular hunting for a hunt group, alternate local and remote members as much as possible. Avoid long sequences of remote members, one after the other, in a circular group. This configuration can take longer to present a call to an available agent.

• The RDN must be the correct device type for the hunt group (station or Broadcast Group A directory number programmed to appear on multiple devices constitutes a broadcast group. There are two types of broadcast groups: Non-Prime Line and Prime Line. A Non-Prime Line group is a directory number programmed on one or more devices that is not the prime line on any device. A Prime Line group is a directory number programmed on button 0 of a phone. Server-based variants of MiVoice Business that use x86 processors, MiVoice Business for Industry Standard Servers MCD-ISS), Multi-instance MiVoice Business, and Virtual MiVoice Business, up to 250 appearances of the directory number can appear on one or more devices. For all other 3300 ICP/MiVoice Business call control platforms, up to 32 appearances of the directory number may appear on one or more devices.). If an RDN is deleted from the Remote Directory Numbers form, it is also deleted from any hunt groups to which it belongs.

• Speedcall members whose ARS routes do not translate to supported trunk types will not be called as Hunt Group candidates. If a system speed call is deleted from the System Speed Calls form, it is also deleted from ay hunt groups to which it belongs.

• Camp-on and Callback are not allowed to network hunt groups.

• When a user performs a transfer to a Network Hunt Group,  there may be a short delay before the Release softkey appears in the set display. The Release softkey is not presented until a free member is found.

• An attendant cannot release a caller to a busy network hunt group (because Campon is not allowed to a hunt group that has one or more remote members).

• If an IP Console application( MiVoice Business Console) user transfers a call to a Network Hunt Group, the user cannot retrieve the call while the system is hunting the group for an idle member. After the call begins ringing an idle member, the user can retrieve the call from the Transferred Call queue. If all members in the Network Hunt Group are either busy or do not answer (before the Call Forward - No Answer Timer expires) the console is recalled.

• On the local controller, SMDR functions the same for network hunt groups as it does for local hunt groups. If the remote members are hosted on systems with 3300 ICP Release 7.0 or later software, SMDR logs are only recorded on the controller that hosts the network hunt group. However, if the network hunt group contains remote members that are hosted on systems with pre-Release 7.0 software, SMDR logs will also be generated on the remote system. In this case, additional logs will be generated for incoming calls that are answered, busy, or unavailable (no answer).

• If RDN Synchronization is supported in the cluster, you can add, delete, or change (renumber) directory numbers that are members of cluster call pickup groups from the User and Services Configuration form.

• SMDR logs are generated at the hunt group controller switch and at the remote member switch after a remote member answers the call. A log is generated at the hunt group controller switch in the following format:

01/25 07:59P 0000:00:04   16130    22216130  16716    A X9999   161   16116130   A1610013 A

A similar log is generated for the incoming call at the remote member switch. For examples of SMDR logs, see Local and Network_Hunt_Group_SMDR_Examples.

• Also refer to the Dialed Call Pickup Conditions.

• Also refer to the Hunt Group Conditions.

Operation

None